Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cura 11099 nozzle switch duration #1981

Merged
merged 3 commits into from
Nov 14, 2023
Merged

Conversation

casperlamboo
Copy link
Contributor

Description

This PR adds the following settings

  • Extruder start gcode duration
  • Extruder end gcode duration
    By entering a duration (expressed in seconds) for this setting the amount of time is added to the time estimation for a nozzle switch. This makes it possible to more accurately tune print time estimations, especially for printers that have longer nozzle switching sequences. Both these settings default to 0; if no value is entered no amount of time is added to the print time estimations.

Screenshot 2023-11-13 at 10 49 49

Also see Cura PR: Ultimaker/Cura#17301

CURA-11099

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Printer definition file(s)
  • Translations

How Has This Been Tested?

Yas

Test Configuration:

  • Operating System: MacOS 13

Checklist:

Copy link
Contributor

github-actions bot commented Nov 13, 2023

Unit Test Results

26 tests   26 ✔️  6s ⏱️
  1 suites    0 💤
  1 files      0

Results for commit a875046.

♻️ This comment has been updated with latest results.

There's still a failure happening _sometimes_ (sigh) but that isn't related to the current ticket as far as I can see.

part of CURA-11099
@rburema rburema merged commit cf3e685 into main Nov 14, 2023
15 of 17 checks passed
@rburema rburema deleted the CURA-11099-nozzle-switch-duration branch November 14, 2023 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants